home *** CD-ROM | disk | FTP | other *** search
- Path: ix.netcom.com!netnews
- From: "William D. Ball" <mrblue@ix.netcom.com>
- Newsgroups: alt.comp.periphs.mainboard.tyan,comp.dcom.modems
- Subject: Re: USR Sportster VI vs Tyan Titan III
- Date: Wed, 07 Feb 1996 17:48:15 -0800
- Organization: Ortho Biotech
- Message-ID: <3119565F.5FAF@ix.netcom.com>
- References: <4f81n4$rsh@nntp.interaccess.com>
- NNTP-Posting-Host: wck-ca6-12.ix.netcom.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-NETCOM-Date: Wed Feb 07 5:48:51 PM PST 1996
- X-Mailer: Mozilla 2.0b5 (Win95; I)
-
- Henry Barta wrote:
- >
- > Has anyone else tried using a USR Sportster VI 33600 on a Tyan
- > Titan III motherboard??? (Internal version of the modem)
- > Yes, I have COM1 disabled in the AWARD bios.
- >
- > Had to configure as Plug and Pr^Hlay for Win95, otherwise it
- > doesn't see modem and I could see no way to force it to recognize
- > COM1.
- >
- > I have installed both modems as PnP under Win95 using the latest
- > mdmusrvi.inf in \Windows\inf and the first modem was identified
- > as Sportster 33600 VI while the second came up as Sportster
- > 28000 VI.
- >
- > Using PnP, have to 'force' load the OS/2 COM.SYS driver by
- > explicitly specifying the hardware address '(1,3F8,4)' or the
- > driver does not load. (OS/2 Sysinfo reports a 2K send buffer
- > and 5K receive Buffer for this modem!)
- >
- > The modem ships as a USR Sportster VI 28.8, but the 10/13/95
- > Supervisor ROM ID's it as a 33600. (And no, the box label does
- > not say V.34+)
- >
- > I suspect a motherboard incompatibility, since I can't believe
- > that USR would ship a product with such obvious problems.
- >
- > Any other experiences or help greatly appreciated.
- >
- > --
- > Hank Barta White Oak Software Inc.
- > hbarta@interaccess.com Predictable Systems by Design.
- > Beautiful Sunny Winfield, Illinois
-
- Mine works fine and I did not disable any ports in BIOS. Maybe that's
- peculiar to OS/2, about which I know nothing. The board is probably not
- the problem, but some port conflict. Also, I had two bad modems (no
- dialtone) before I got a good one.
-
- Bill
-